Repository navigation
build(deps): bump zod from 4.4.3 to 4.6.6 - #277
Conversation
|
| "just-bash": "^3.0.1", | ||
| "vite": "^6.0.0 || ^7.0.0 || ^8.0.0", | ||
| "zod": "^4.4.3" | ||
| "zod": "^4.6.6" |
There was a problem hiding this comment.
🟡 Peer requirement lacks a release entry
The zod peer minimum rises to 4.6.6 without a changeset for the released package. The release workflow cannot record this compatibility change in its versioned changelog.
Learn more
The package's optional Zod peer is part of its published installation contract. Raising its minimum affects consumers using the tools entry points with Zod 4.4.x through 4.6.5. COLLABORATORS release guidance requires a changeset when a released package changes. The release workflow uses pending changesets to generate versioned release notes.
Example: An application using Zod 4.4.3 upgrades @cloudflare/computer and encounters the new peer constraint; the package's release notes do not mention the constraint change.
Recommended fix: Add a changeset for @cloudflare/computer describing the raised Zod peer minimum, with a version bump appropriate to the compatibility policy.
Was this helpful? React with 👍 or 👎 to provide feedback.
92a4945 to
54344e0
Compare
|
The |
|
@ask-gardener can you open a separate PR that bumps zod and fixes the failing tests. |
54344e0 to
737a459
Compare
|
One check failed on this update:
The same |
737a459 to
d4b60cf
Compare
|
18 checks failed on this update:
|
commit: |
Bumps [zod](https://github.com/colinhacks/zod) from 4.4.3 to 4.6.6. - [Release notes](https://github.com/colinhacks/zod/releases) - [Commits](colinhacks/zod@v4.4.3...v4.6.6) --- updated-dependencies: - dependency-name: zod dependency-version: 4.6.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
@cloudflare/vitest-pool-workers pins zod to exactly 4.4.3, so with the workspaces asking for ^4.6.6, npm kept 4.4.3 at the root and gave each workspace its own 4.6.6. @cloudflare/codemode and the MCP SDK resolve zod from the root, so they read schemas built with the other copy: the MCP example's tools/list failed with "Cannot read properties of undefined (reading 'push')". The root now asks for ^4.6.6 itself, so 4.6.6 is the one copy every workspace and its dependencies share, and vitest-pool-workers keeps its own 4.4.3.
368f74b to
3617d4a
Compare
Bumps zod from 4.4.3 to 4.6.6.
Release notes
Sourced from zod's releases.
... (truncated)
Commits
9c21983ci: stage at verbose so a failed OIDC token exchange says why529f78d4.6.6a0ebf97fix(v4): check array, set and map size bounds before parsing elements (#6652)a2ba4a6fix(types): declare record output and input as members, not base type argumen...c42596brelease: hold the run on the release-approval environment until the staged ve...bacad51docs: square the Code for Japan logo to match the other bronze tiles8fb2fafdocs: crop the Code for Japan logo and list it first in bronzeb2ef983docs: add Code for Japan to bronze sponsors74304cerelease: stage npm versions instead of publishing them (#6622)34a626fdocs: tighten the z.locales tree-shaking note